The MDIS server must verify the integrity of all operating system files, device drivers, and security enforcement mechanisms at startup and at least every six hours thereafter, using one or more DoD approved cryptographic mechanisms that compare attributes of the operating system configuration to a known good baseline.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-32758	WIR-WMS-MDIS-11	SV-43104r1_rule	DCSS-2	High

Description
Detection of possible compromise of a DoD mobile device is a key security control to insure the compromise does not result in the exposure of sensitive DoD data or lead to a successful attack on the DoD network. Analysis has determined scans must be performed at least every 6 hours.

STIG	Date
Mobile Device Integrity Scanning (MDIS) Server Security Technical Implementation Guide (STIG)	2012-07-20

Details

Check Text ( C-41091r4_chk )
Verify the MDIS server and agent verify the integrity of all operating system files, device drivers, and security enforcement mechanisms at startup and at least every six hours thereafter using one or more DoD approved cryptographic mechanisms that compare attributes of the operating system configuration to a known good baseline. Talk to the site system administrator and have them show this capability exists in the MDIS server. Also, review MDIS product documentation. Mark as a finding if the MDIS server does not have required features.

Check Text ( C-41091r4_chk )

Verify the MDIS server and agent verify the integrity of all operating system files, device drivers, and security enforcement mechanisms at startup and at least every six hours thereafter using one or more DoD approved cryptographic mechanisms that compare attributes of the operating system configuration to a known good baseline. Talk to the site system administrator and have them show this capability exists in the MDIS server. Also, review MDIS product documentation.

Mark as a finding if the MDIS server does not have required features.

Fix Text (F-36640r3_fix)
Use a MDIS product that verifies the integrity of all operating system files, device drivers, and security enforcement mechanisms at startup and at least every six hours thereafter using one or more DoD approved cryptographic mechanisms that compare attributes of the operating system configuration to a known good baseline and enable the features.